fix(deps): update dependency org.mockito:mockito-core to v5 #373
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
8c0700c
to
09f24c6
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
026b285
to
bb3774a
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
18cca02
to
0856c42
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
0856c42
to
95119be
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
95119be
to
367b82b
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
cbcd405
to
82d7374
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
82d7374
to
5da1440
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
5da1440
to
9154bc8
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
3 times, most recently
from
75cc780
to
970cbb2
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
970cbb2
to
20053cf
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
20053cf
to
40c7925
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
40c7925
to
98575d5
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
98575d5
to
31b6369
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
31b6369
to
5426394
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
5426394
to
dc36c26
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
3 times, most recently
from
1d32777
to
26f32cd
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
b0fc9fb
to
a5508b3
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
a5508b3
to
d92a95f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.11.0->5.14.2Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
mockito/mockito (org.mockito:mockito-core)
v5.14.2Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.2
mockito-prefix (#3460)v5.14.1Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.1
v5.14.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.0
v5.13.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.13.0
Only.verifythrowsNullPointerException(#3237)v5.12.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.12.0
AdditionalMatchers.and()andAdditionalMatchers.or()not to swap the order of matchers (#3335)v5.11.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.11.0
@Captortest parameters don't work with primitive type arguments (#3229)v5.10.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.10.0
v5.9.0Compare Source
What's Changed
New Contributors
Full Changelog: mockito/mockito@v5.8.0...v5.9.0
v5.8.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.8.0
v5.7.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.7.0
0.8.11(#3147)v5.6.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.6.0
Optionalis notemptywhen usingRETURN_DEEP_STUBS(#2865)v5.5.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.5.0
v5.4.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.4.0
@Mock(serializable = true)for parameterized types. (#3007)ArgumentMatchers#any()JavaDoc(#3003)
@Mock(serializable = true)no longer works with parameterized types (#2979)v5.3.1Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.3.1
v5.3.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.3.0
withoutAnnotationsparameter to@Mock(#2965)ArgumentMatchers#assertArgmethod. (#2949)v5.2.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.2.0
v5.1.1Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.1.1
v5.1.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.1.0
CONTRIBUTING.md(#2870)CONTRIBUTING.md(#2868)Mockito#{mock,spy}(T... reified)with@SafeVarargs(#2866)v5.0.0Compare Source
Mockito 5: prepare for future JDK versions
For a while now, we have seen an increase in problems/incompatibilities with recent versions of the JDK due to our usage of JVM-internal API.
Most notably, JDK 17 made some changes which are incompatible with the current subclass mockmaker.
Therefore, to prepare for the future of JDK, we are making some core changes to ensure Mockito keeps on working.
Switch the default mockmaker to
mockito-inlineBack in Mockito 2.7.6, we published a new mockmaker based on the "inline bytecode" principle.
This mockmaker creates mocks manipulating bytecode equivalent within the original class such that its method implementations hook into the normal Mockito machinery.
As a comparison, the subclass mockmaker generates "real" subclasses for mocks, to mimic the same behavior.
While the approaches are similar, the inline mockmaker avoids certain restrictions that the JDK imposes.
For example, it does not violate module boundaries (introduced in JDK 9, but more heavily used in JDK 17) and avoids the leaking of the creation of the subclass.
Massive thanks to community member @reta who implemented this change.
Note: this does not affect
mockito-androidnor testing on Android.When should I still be using the subclass mockmaker?
There are legitimate remaining use cases for the subclass mockmaker.
For example, on the Graal VM's native image, the inline mockmaker will not work and the subclass mockmaker is the appropriate choice.
Additionally, if you would like to avoid mocking final classes, using the subclass mockmaker is a possibibility.
Note however that if you solely want to use the subclass mockmaker to avoid mocking final, you will run into the above mentioned issues on JDK 17+.
We want to leave this choice up to our users, which is why we will keep on supporting the subclass mockmaker.
If you want to use the subclass mockmaker instead, you can use the new
mockito-subclassartifact (published on Maven Central along with all our other artifacts).Update the minimum supported Java version to 11
Mockito 4 supports Java 8 and above.
Similar to other open source projects, we are moving away from JDK 8 and to newer versions.
The primary reason for moving away from JDK 8 is the increasing maintenance costs with keeping our own infrastructure working.
Lately we have been running into more and more JDK 8 breakages.
Additionally, while we want to support the newest JDK API's, our current solution to support both JDK 8 and newer versions causes issues with the
SecurityManager.Since we want Mockito to work on the newest version and more and more business
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.